<html>

<head>
<meta http-equiv="Content-Language" content="en-us">
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<title>Customer Meeting on April 4</title>
</head>

<body>

<p align="center"><b><font size="5">Customer Meeting on May 11, 2007</font></b></p>
<p align="left">The last customer meeting went well. The project was first demoed, and a review of how it all functioned, showing of code as well as answering any questions of code and of the Google project hosting.  First thing that came out of his mouth was "I think its great".</p>
<p align="left"><b>Features shown to customers:</b></p>

<ol>
  <li>

<p align="left">Suggestion 1 (set focus on drop-down lists) from the previous
meeting was implemented.&nbsp; However, this feature works well on Firefox but
doesn't work very well on Internet Explorer.&nbsp; On Internet Explorer, when
the focus is set to a drop-down list, the user is not able to user to auto
complete feature.&nbsp; When the user types in the first letter of an item, the
drop-down list doesn't show that item as selected item.</p>

  </li>
  <li>

<p align="left">Suggestion 2 (Bookmark and History) from previous meeting was
implemented.&nbsp; The customer, Gary, likes it.</p>

  </li>
  <li>

<p align="left">User Interface for searching by attributes was shown to the
customer.&nbsp; He likes it. </p>

  </li>
</ol>

<p align="left"><b>Customer's Feedback and Suggestions: </b></p>

<ol>
  <li>

<p align="left">After showing Gary the customer what we finished and asking if we could improve upon what we have he said that he liked the idea of a simple UI interface.  Since people, when given too many options that they don't nessarly care about wouldn't use it. But it would be nice to have those &quot;advanced&quot; features. So he sujested that we have a hidden advance option that droped down when clicked. This would keep the UI looking simple and not bother people who don't care about those things to not be overwelmed.</p>
  </li>
  <li>

<p align="left">For searching by attributes, users may want to search by
multiple focus requirements.&nbsp; For example, a user may want to search for a
class the fulfill both WI and OC.&nbsp; Right now, our application doesn't not
allow the users to do this kind of search.&nbsp; We were unable to complete that feature in the procedure call with in the time frame. We listed all focus
requirements in a drop-down list.&nbsp; Gary suggested that these focus
requirements should not be placed in a drop-down list because even when we make
the drop-down list multiple select, the users may not know that the drop-down
list has this features.&nbsp; Rather, we should place these focus requirements
in check boxes.</p>
  </li>
</ol>

<p align="left"><b>Future headings: </b> These are the areas which if the project were to be continued this is the direction in which we would have liked to have seen it go.</p>

<ol>
  <li>Complete search by attributes
    <ul><li> Searching for attributes.  The stored procedure was completed but was not added to page.</li>
        <li> Multiple attribute searches. If a user wanted to find a class with both a WI and a FG and any other attribute. 
        It would return all matching.</li></ul>
  </li>
  <br>
  <li>Search by Instructor
  	<ul><li>Searching for Instructor by first or last name.</li>
    		<li>A new stored procedure will have to be created where columns of instructor, room, time and days are created.</li></ul>
  </li>
  <br>
  <li>Class course discription
    <ul><li>After searching for a class the classes shown would be clickable and whould open up a new page that displayed the course 			 						catalog discription.</li>
      	<li>Currently we didn't know how to accquire that data.  From our understanding that info is apart of a different database  		 						under another departments control</li>
   	</ul>
  </li>
  <br>
  <li>Searching by Time</li>
</ol>

<p align="left">On another note we might have a meeting to discus further implimentation of the project continuing into the summer.  This is still and idea and team members will take some time thinking about it.  All and all the customer love the project and the idea that it represents.  He is curious to find out how GWT's structure can handle large scale use.</p>

<p align="center">&nbsp;</p>

<p align="center"><b><font size="5">Customer Meeting on April 12, 2007</font></b></p>

<p align="left"><b>Features shown to customers:</b></p>

<ol>
  <li>

<p align="left">Suggestion 2 from the previous meeting was implemented.&nbsp;
The application prompts users that new data is loading while users requests are
sending to the server.</p>

  </li>
  <li>

<p align="left">Suggestion 3 from the previous meeting was implemented.&nbsp;
The Semester drop-down list now lists all the semester from Summer 2003 to
Spring Extension 2007.&nbsp; Semesters later than Spring Extension 2007 are not
listed because data in our development database is not up-to-date.</p>

  </li>
  <li>

<p align="left">Suggestions 1 and 4 from the previous meeting were not
implemented this time.</p>

  </li>
</ol>

<p align="left"><b>Customer's Feedback and Suggestions: </b></p>

<ol>
  <li>

<p align="left">We should set the keyboard and mouse focus to the first
drop-down list (Campus drop-down list) when the program first loaded.&nbsp; In
this way, users can start to search right away.&nbsp; They don't have to hit the
Tab key or click on the Campus drop-down list to start there search.</p>

  </li>
  <li>

<p align="left">We should provide History and Bookmark features so users are
able to bookmark their searches and click the browser Back button to go back to
their previous searches.</p>

  </li>
</ol>

<p align="center"><b><font size="5">Customer Meeting on April 09, 2007</font></b></p>

<p align="left"><b>Features shown to customer:</b></p>

<ol>
  <li>

<p align="left">We implemented suggestion 1 from the previous meeting.&nbsp; All
the drop-down lists now have the auto-complete features. The customer was happy
with it</p>

  </li>
  <li>

<p align="left">Suggestions 2 and 3 from the previous meeting were not
implemented this time because it involves a lot of work in the database which we
have to work together with to customer.&nbsp; He is very busy and he needs time
to create&nbsp; new stored procedures.</p>

  </li>
</ol>

<p align="left"><b>Customer's Feedback and Suggestions: </b></p>

<ol>
  <li>

<p align="left">Talked to the customer today about how we would implement the Search
By Attribute feature. We came up with an idea that we should place the attribute
drop-down list before the subject drop-down list. This way the attributes can
filter the subjects. </p>

  </li>
  <li>

<p align="left">He also said that I should have something to let the user know the the search is
loading. This is necessary for an Ajax application because most items on the
page don't change. We should prompt the user that new info is loaded. </p>

  </li>
  <li>

<p align="left">He also recommended that we should shown past semesters in the
Semesters drop-down list.&nbsp; It will make it convenient for users who want to
look back at past semesters for reference.</p>

  </li>
  <li>

<p align="left">Currently, the application can't search for courses from Spring 2007 or later. He
said he will update the database to for the current data.</p>

  </li>
</ol>

<p align="center">&nbsp;</p>

<p align="center"><b><font size="5">Customer Meeting on April 4, 2007</font></b></p>
<p align="left">We went over the project&nbsp; for about 10 minutes.&nbsp; The
customer (Gary) said that it was faster to have this much work done than he
expected.&nbsp; The reason was that we used Google Web Toolkit (GWT) framework
instead of manually writing Javascript.&nbsp; He wrote Javascript for all of his
Ajax project.&nbsp; He was also impressed about the way we deployed the project.&nbsp;
Our project was distributed as a WAR file.&nbsp; We could deploy the project on
any computer that has Tomcat installed in less than 5 minutes.&nbsp; There is no
need to configure the web.xml for Tomcat. </p>
<p align="left">Customer's feedback and suggestions:</p>
<ol>
  <li>
  <p align="left">Because there are lots of subjects listed in the Subject
  drop-down list, we should add the auto-complete feature to the drop-down list
  so the user can just type the first letter of the subject they want and get
  the full name shown right below it.</li>
  <li>
  <p align="left">If we try to add a lot of search criteria on the same page, it
  would take a lot of time for the users who don't need them.&nbsp; Instead, we
  provide a separate search section&nbsp; for&nbsp; users who need to do an
  advance search such as search courses by instructors, by times, by dates, etc.&nbsp;
  Thus, on our homepage, we will let users do a search for courses by attributes
  (DS, DH, A, B) or by subjects (History, Math, English, etc..) and a link or
  any mechanism that give users an Advance search option.</li>
  <li>
  <p align="left">He said if he was the designer, he would not use full names
  for the subjects.&nbsp; For example, he said if people they don't know what
  ICS is, the should not take the course.&nbsp; He said he may be wrong. I can
  do whatever I want.</li>
</ol>

<p align="left">&nbsp;</p>
<p align="center"><b><font size="5">Customer Meeting on March 01, 2007</font></b></p>
<div id="wikicontent">
  <strong>Purpose:</strong> To display a demonstration of the current project
  status.
  <h3>Meeting Summary:</h3>
  <p><strong>Customer was impressed with current progress.</strong> </p>
  <p><strong>Review of current status.</strong> </p>
  <p><strong>Future heading:</strong> </p>
  <ol>
    <li>expanding current application with the UH devDatabase. </li>
    <li>implement a component at a time. </li>
    <li>acquired UH devDatabase connection. </li>
    <li>now we can examen procedure calls for future extraction of attributes,
    using current procedures as much as possible. </li>
  </ol>
</div>

</body>

</html>